Vibration sensing system and method for categorizing portable device context and modifying device operations

ABSTRACT

Disclosed herein are methods for operating a computing device including determining an amount of pressure exerted on a touch-sensitive surface of the computing device. According to the various embodiments, a touch input is received by the touch-sensitive surface. The amount of pressure exerted by the touch input on the touch-sensitive surface is then determined. The computing device operates in a first manner when a first amount of pressure is received and operates in a second manner when a second amount of pressure is received.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.13/196,834, filed Aug. 2, 2011, now U.S. Pat. No. 8,892,162, whichclaims the benefit under 35 U.S.C. §119(e) of U.S. Provisional PatentApplication No. 61/478,893, filed on Apr. 25, 2011, both of which areincorporated by reference as if fully disclosed herein.

TECHNICAL FIELD

This relates generally to electronic devices with touch-sensitivesurfaces, including but not limited to electronic devices that detecttouches based on vibration sensing.

BACKGROUND

The use of touch-sensitive surfaces as input devices for computers andother electronic computing devices has increased significantly in recentyears. Exemplary touch-sensitive surfaces include touch pads and touchscreen displays. Such surfaces are widely used to manipulate userinterface objects on a display.

SUMMARY

New devices and methods for categorizing context of a device (e.g.,environment of the device or status of the user) are described. Suchmethods and interfaces may complement or replace device operations,including conventional methods for manipulating user interface objects.Such methods and interfaces reduce the cognitive burden on a user andproduce a more efficient human-machine interface.

In some embodiments, the device is portable (e.g., a notebook computer,tablet computer, or handheld device). In some embodiments, the devicehas a touch-sensitive display (also known as a “touch screen” or “touchscreen display”). In some embodiments, the device has a touchpad. Insome embodiments, the device has a graphical user interface (GUI), oneor more processors, memory and one or more modules, programs or sets ofinstructions stored in the memory for performing multiple functions. Insome embodiments, the user interacts with the GUI primarily throughfinger contacts and gestures on the touch-sensitive surface. In someembodiments, the functions may include image editing, drawing,presenting, word processing, website creating, disk authoring,spreadsheet making, game playing, telephoning, video conferencing,e-mailing, instant messaging, workout support, digital photographing,digital videoing, web browsing, digital music playing, and/or digitalvideo playing. Executable instructions for performing these functionsmay be included in a non-transitory computer readable storage medium orother computer program product configured for execution by one or moreprocessors.

In accordance with some embodiments, a portable device includes: anenclosure; one or more processors for executing one or more programs;one or more actuators in or on the enclosure for generating mechanicalvibrations; one or more sensors in or on the enclosure for detectingmechanical vibrations; and memory storing one or more programs forexecution by the one or more processors. The one or more programsinclude: instructions for analyzing one or more signals produced by theone or more sensors with respect to mechanical vibrations to determine aholding state of the portable device; and instructions for modifyingoperation of at least one application executed by the one or moreprocessors in accordance with the determined holding state.

In accordance with some embodiments, a portable telephone deviceincludes: an enclosure; one or more processors for executing one or moreprograms; one or more actuators in or on the enclosure for generatingmechanical vibrations; one or more sensors in or on the enclosure fordetecting mechanical vibrations; and memory storing one or more programsfor execution by the one or more processors. The one or more programsinclude: instructions for analyzing one or more signals produced by theone or more sensors with respect to mechanical vibrations to determine aholding state of the portable telephone device; and instructions forconditionally answering an incoming call in accordance with a change inthe determined holding state of the portable telephone device.

In accordance with some embodiments, a method is performed at a portabledevice that includes an enclosure, one or more processors for executingone or more programs, one or more actuators in or on the enclosure, oneor more sensors in or on the enclosure, and memory storing one or moreprograms for execution by the one or more processors. The methodincludes: generating mechanical vibrations with the one or moreactuators; detecting mechanical vibrations with the one or more sensors;analyzing one or more signals produced by the one or more sensors withrespect to mechanical vibrations to determine a holding state of theportable device; and modifying operation of at least one applicationexecuted by the one or more processors in accordance with the determinedholding state.

In accordance with some embodiments, a method is performed at a portabletelephone device that includes an enclosure, one or more processors forexecuting one or more programs, one or more actuators in or on theenclosure, one or more sensors in or on the enclosure, and memorystoring one or more programs for execution by the one or moreprocessors. The method includes: generating mechanical vibrations withthe one or more actuators; detecting mechanical vibrations with the oneor more sensors; analyzing one or more signals produced by the one ormore sensors with respect to mechanical vibrations to determine aholding state of the portable telephone device; and conditionallyanswering an incoming call in accordance with a change in the determinedholding state of the portable telephone device.

In accordance with some embodiments, a non-transitory computer-readablestorage medium stores one or more programs for execution by one or moreprocessors of a portable device that includes an enclosure, one or moreactuators in or on the enclosure, and one or more sensors in or on theenclosure. The one or more programs include instructions for performingany of the above methods.

In accordance with some embodiments, a portable device includes: anenclosure; one or more processors for executing one or more programs;one or more actuators in or on the enclosure for generating mechanicalvibrations; one or more sensors in or on the enclosure for detectingmechanical vibrations; and memory storing one or more programs forexecution by the one or more processors. The one or more programsinclude instructions for performing any of the above methods.

In accordance with some embodiments, a portable device includes: anenclosure; means for generating mechanical vibrations; means fordetecting mechanical vibrations; and means for performing any of theabove methods.

In accordance with some embodiments, an information processing apparatusfor use in a portable device with an enclosure, one or more actuators inor on the enclosure, and one or more sensors in or on the enclosure,includes means for performing any of the above methods.

In accordance with some embodiments, a portable device includes anactuator unit for generating mechanical vibrations; a sensor unit fordetecting mechanical vibrations; and a processing unit coupled to theactuator unit and the sensor unit. The processing unit is configured to:analyze one or more signals produced by the sensor unit with respect tomechanical vibrations to determine a holding state of the portabledevice; and modify operation of at least one application executed by theprocessing unit in accordance with the determined holding state.

In accordance with some embodiments, a portable telephone deviceincludes: an actuator unit for generating mechanical vibrations; asensor unit for detecting mechanical vibrations; and a processing unitcoupled to the actuator unit and the sensor unit. The processing unit isconfigured to: analyze one or more signals produced by the sensor unitwith respect to mechanical vibrations to determine a holding state ofthe portable device; and conditionally answer an incoming call inaccordance with a change in the determined holding state of the portabletelephone device.

Thus, portable devices with actuators and vibration sensors enablefaster, more efficient human-machine interfaces, thereby increasing theeffectiveness, efficiency, and user satisfaction with such devices. Suchmethods and interfaces may complement or replace conventionalhuman-machine interfaces.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the aforementioned embodiments of theinvention as well as additional embodiments thereof, reference should bemade to the Description of Embodiments below, in conjunction with thefollowing drawings in which like reference numerals refer tocorresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIGS. 2A-2E illustrate a portable device in accordance with someembodiments.

FIG. 3 illustrates exemplary actuator input and exemplary sensor signalin accordance with some embodiments.

FIGS. 4A-4C are flow diagrams illustrating a method of conditionallymodifying operation of a portable device in accordance with a holdingstate in accordance with some embodiments.

FIG. 5 is a flow diagram illustrating a method of conditionallyanswering an incoming call in accordance with a change in a holdingstate in accordance with some embodiments.

FIG. 6 is a functional block diagram of a portable electronic device inaccordance with some embodiments.

FIG. 7 is a functional block diagram of a portable telephone device inaccordance with some embodiments.

DETAILED DESCRIPTION

Determining the context of a device (e.g., whether the device is heldtightly or loosely, whether the device is held by a user or stored in apocket, whether the device is carried by a user walking on stairs,whether the device is carried by a running user, etc.) can improvehuman-machine interface. In some embodiments, such determination isaccomplished using components commonly found in portable electronicdevices. For example, actuators and sensors within a mobile phone may beused to determine the context of the mobile phone. Therefore, themethods and devices described herein may be easily implemented intoexisting portable devices.

Below, FIGS. 1A-1B and 2A-2E provide a description of exemplary devices.FIG. 3 illustrates exemplary signals provided to actuator(s) anddetected by sensor(s) of exemplary devices. FIGS. 4A-4C are flowdiagrams illustrating a method of conditionally modifying operation ofan exemplary device. FIG. 5 is a flow diagram illustrating a method ofconditionally answering an incoming call at an exemplary device.

Exemplary Devices

Reference will now be made in detail to embodiments, examples of whichare illustrated in the accompanying drawings. In the following detaileddescription, numerous specific details are set forth in order to providea thorough understanding of the present invention. However, it will beapparent to one of ordinary skill in the art that the present inventionmay be practiced without these specific details. In other instances,well-known methods, procedures, components, circuits, and networks havenot been described in detail so as not to unnecessarily obscure aspectsof the embodiments.

It will also be understood that, although the terms first, second, etc.may be used herein to describe various elements, these elements shouldnot be limited by these terms. These terms are only used to distinguishone element from another. For example, a first contact could be termed asecond contact, and, similarly, a second contact could be termed a firstcontact, without departing from the scope of the present invention. Thefirst contact and the second contact are both contacts, but they are notthe same contact.

The terminology used in the description of the invention herein is forthe purpose of describing particular embodiments only and is notintended to be limiting of the invention. As used in the description ofthe invention and the appended claims, the singular forms “a”, “an” and“the” are intended to include the plural forms as well, unless thecontext clearly indicates otherwise. It will also be understood that theterm “and/or” as used herein refers to and encompasses any and allpossible combinations of one or more of the associated listed items. Itwill be further understood that the terms “includes,” “including,”“comprises,” and/or “comprising,” when used in this specification,specify the presence of stated features, integers, steps, operations,elements, and/or components, but do not preclude the presence oraddition of one or more other features, integers, steps, operations,elements, components, and/or groups thereof.

As used herein, the term “if” may be construed to mean “when” or “upon”or “in response to determining” or “in response to detecting,” dependingon the context. Similarly, the phrase “if it is determined” or “if [astated condition or event] is detected” may be construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touch pads), may also beused. It should also be understood that, in some embodiments, the deviceis not a portable communications device, but is a desktop computer witha touch-sensitive surface (e.g., a touch screen display and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device may include one or moreother physical user-interface devices, such as a physical keyboard, amouse and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that may be executed on the device may use atleast one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the device maybe adjusted and/or varied from one application to the next and/or withina respective application. In this way, a common physical architecture(such as the touch-sensitive surface) of the device may support thevariety of applications with user interfaces that arc intuitive andtransparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive displays 112 inaccordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience, and may also be knownas or called a touch-sensitive display system. Device 100 may includememory 102 (which may include one or more computer readable storagemediums), memory controller 122, one or more processing units (CPU's)120, peripherals interface 118, RF circuitry 108, audio circuitry 110,speaker 111, microphone 113, input/output (I/O) subsystem 106, otherinput or control devices 116, and external port 124. Device 100 mayinclude one or more optical sensors 164. These components maycommunicate over one or more communication buses or signal lines 103.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 may have more orfewer components than shown, may combine two or more components, or mayhave a different configuration or arrangement of the components. Thevarious components shown in FIG. 1A may be implemented in hardware,software, or a combination of both hardware and software, including oneor more signal processing and/or application specific integratedcircuits.

Memory 102 may include high-speed random access memory and may alsoinclude non-volatile memory, such as one or more magnetic disk storagedevices, flash memory devices, or other non-volatile solid-state memorydevices. Access to memory 102 by other components of device 100, such asCPU 120 and the peripherals interface 118, may be controlled by memorycontroller 122.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data.

In some embodiments, peripherals interface 118, CPU 120, and memorycontroller 122 may be implemented on a single chip, such as chip 104. Insome other embodiments, they may be implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 may include well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 may communicate with networks, such as the Internet, alsoreferred to as the World Wide Web (WWW), an intranet and/or a wirelessnetwork, such as a cellular telephone network, a wireless local areanetwork (LAN) and/or a metropolitan area network (MAN), and otherdevices by wireless communication. The wireless communication may useany of a plurality of communications standards, protocols andtechnologies, including but not limited to Global System for MobileCommunications (GSM), Enhanced Data GSM Environment (EDGE), high-speeddownlink packet access (HSDPA), high-speed uplink packet access (HSUPA),wideband code division multiple access (W-CDMA), code division multipleaccess (CDMA), time division multiple access (TDMA), Bluetooth, WirelessFidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g and/orIEEE 802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocolfor e-mail (e.g., Internet message access protocol (IMAP) and/or postoffice protocol (POP)), instant messaging (e.g., extensible messagingand presence protocol (XMPP), Session Initiation Protocol for InstantMessaging and Presence Leveraging Extensions (SIMPLE), Instant Messagingand Presence Service (IMPS)), and/or Short Message Service (SMS), or anyother suitable communication protocol, including communication protocolsnot yet developed as of the filing date of this document.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data may be retrievedfrom and/or transmitted to memory 102 and/or RF circuitry 108 byperipherals interface 118. In some embodiments, audio circuitry 110 alsoincludes a headset jack. The headset jack provides an interface betweenaudio circuitry 110 and removable audio input/output peripherals, suchas output-only headphones or a headset with both output (e.g., aheadphone for one or both ears) and input (e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 may include display controller 156 andone or more input controllers 160 for other input or control devices.The one or more input controllers 160 receive/send electrical signalsfrom/to other input or control devices 116. The other input devices 116include vibration sensor(s) 129. In some embodiments, vibrationsensor(s) 129 include accelerometer(s) 168. In some embodiments,vibration sensor(s) 129 include one or more of: piezoelectric vibrationsensors (e.g., piezoelectric displacement sensors, and/or piezoelectricvelocity sensors), and micro-electro-mechanical system (MEMS) vibrationsensors. In some embodiments, vibration sensor(s) 129 include one ormore gyroscopes and/or one or more compasses. In some embodiments,vibration sensor(s) 129 include one or more microphones. In someembodiments, vibration sensor(s) 129 include at least one optical system(e.g., a laser aligned with a photodiode). Such optical system, which ishighly sensitive to vibrations, can be used to give an accurate measureof vibrations. The other input devices 116 may also include one or moreof: physical buttons (e.g., push buttons, rocker buttons, etc.), dials,slider switches, joysticks, click wheels, and so forth. In somealternate embodiments, input controller(s) 160 may be coupled to any (ornone) of the following: a keyboard, infrared port, USB port, and apointer device such as a mouse. The one or more buttons may include anup/down button for volume control of speaker 111 and/or microphone 113.The one or more buttons may include a push button.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output may includegraphics, text, icons, video, and any combination thereof (collectivelytermed “graphics”). In some embodiments, some or all of the visualoutput may correspond to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor or set of sensorsthat accepts input from the user based on haptic and/or tactile contact.Touch screen 112 and display controller 156 (along with any associatedmodules and/or sets of instructions in memory 102) detect contact (andany movement or breaking of the contact) on touch screen 112 andconverts the detected contact into interaction with user-interfaceobjects (e.g., one or more soft keys, icons, web pages or images) thatare displayed on touch screen 112. In an exemplary embodiment, a pointof contact between touch screen 112 and the user corresponds to a fingerof the user.

Touch screen 112 may use LCD (liquid crystal display) technology, LPD(light emitting polymer display) technology, or LED (light emittingdiode) technology, although other display technologies may be used inother embodiments. Touch screen 112 and display controller 156 maydetect contact and any movement or breaking thereof using any of aplurality of touch sensing technologies now known or later developed,including but not limited to capacitive, resistive, infrared, andsurface acoustic wave technologies, as well as other proximity sensorarrays or other elements for determining one or more points of contactwith touch screen 112. In an exemplary embodiment, projected mutualcapacitance sensing technology is used, such as that found in theiPhone®, iPod Touch®, and iPad® from Apple Inc. of Cupertino, Calif.

Touch screen 112 may have a video resolution in excess of 100 dpi. Insome embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user may make contact with touch screen 112using any suitable object or appendage, such as a stylus, a finger, andso forth. In some embodiments, the user interface is designed to workprimarily with finger-based contacts and gestures, which can be lessprecise than stylus-based input due to the larger area of contact of afinger on the touch screen. In some embodiments, the device translatesthe rough finger-based input into a precise pointer/cursor position orcommand for performing the actions desired by the user.

In some embodiments, in addition to the touch screen, device 100 mayinclude a touchpad (not shown) for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad may be a touch-sensitive surface that is separatefrom touch screen 112 or an extension of the touch-sensitive surfaceformed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 may include a power management system, oneor more power sources (e.g., battery, alternating current (AC)), arecharging system, a power failure detection circuit, a power converteror inverter, a power status indicator (e.g., a light-emitting diode(LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 may also include one or more optical sensors 164. FIG. 1Ashows an optical sensor coupled to optical sensor controller 158 in I/Osubsystem 106. Optical sensor 164 may include charge-coupled device(CCD) or complementary metal-oxide semiconductor (CMOS)phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lens, and converts the lightto data representing an image. Optical sensor 164 is also configured todetect ambient brightness. In conjunction with imaging module 143 (alsocalled a camera module), optical sensor 164 may capture still images orvideo. In some embodiments, an optical sensor is located on the back ofdevice 100, opposite touch screen display 112 on the front of thedevice, so that the touch screen display may be used as a viewfinder forstill and/or video image acquisition. In some embodiments, anotheroptical sensor is located on the front of the device so that the user'simage may be obtained for videoconferencing while the user views theother video conference participants on the touch screen display.

Device 100 includes one or more actuator(s) 127 for generatingmechanical vibrations. In some embodiments, the one or more actuator(s)127 include one or more motors (e.g., cell phone or pager motors thatgenerate mechanical vibration to indicate incoming calls). In someembodiments, the one or more actuator(s) 127 include speaker 111. Insome embodiments, the one or more actuator(s) 127 include one or morepiezoelectric actuators (e.g., a piezo speaker). In some embodiments,the one or more piezoelectric actuators include at least onepiezoelectric actuator attached (e.g., on one side of the piezoelectricactuator) to an enclosure of device 100 and also connected (e.g., on anopposite side of the piezoelectric actuator) to a mass (e.g., a weightor a component of device 100, such as a cover glass or battery). In someembodiments, actuator 127 includes one or more layers of electroactivepolymers (e.g., electroactive polymers attached to a mass).

Device 100 may also include one or more proximity sensors 166. FIG. 1Ashows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 may be coupled to input controller 160in I/O subsystem 106. In some embodiments, the proximity sensor turnsoff and disables touch screen 112 when the multifunction device isplaced near the user's ear (e.g., when the user is making a phone call).

Device 100 may also include one or more accelerometers 168. The one ormore accelerometers 168 may include one or more single-axisaccelerometers and/or one or more multi-axis (e.g., triaxial)accelerometers. FIG. 1A shows accelerometer 168 coupled to peripheralsinterface 118. Alternately, accelerometer 168 may be coupled to an inputcontroller 160 in I/O subsystem 106. In some embodiments, information isdisplayed on the touch screen display in a portrait view or a landscapeview based on an analysis of data received from the one or moreaccelerometers. Device 100 optionally includes, in addition toaccelerometer(s) 168, a magnetometer (not shown) and a GPS (or GLONASSor other global navigation system) receiver (not shown) for obtaininginformation concerning the location and orientation (e.g., portrait orlandscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments memory 102 stores device/globalinternal state 157, as shown in FIGS. 1A and 3. Device/global internalstate 157 includes one or more of: active application state, indicatingwhich applications, if any, are currently active; display state,indicating what applications, views or other information occupy variousregions of touch screen display 112; sensor state, including informationobtained from the device's various sensors and input devices 116; andlocation information concerning the device's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, oran embedded operating system such as VxWorks) includes various softwarecomponents and/or drivers for controlling and managing general systemtasks (e.g., memory management, storage device control, powermanagement, etc.) and facilitates communication between various hardwareand software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with the30-pin connector used on iPod (trademark of Apple Inc.) devices.

Contact/motion module 130 may detect contact with touch screen 112 (inconjunction with display controller 156) and other touch sensitivedevices (e.g., a touchpad or physical click wheel). Contact/motionmodule 130 includes various software components for performing variousoperations related to detection of contact, such as determining ifcontact has occurred (e.g., detecting a finger-down event), determiningif there is movement of the contact and tracking the movement across thetouch-sensitive surface (e.g., detecting one or more finger-draggingevents), and determining if the contact has ceased (e.g., detecting afinger-up event or a break in contact). Contact/motion module 130receives contact data from the touch-sensitive surface. Determiningmovement of the point of contact, which is represented by a series ofcontact data, may include determining speed (magnitude), velocity(magnitude and direction), and/or an acceleration (a change in magnitudeand/or direction) of the point of contact. These operations may beapplied to single contacts (e.g., one finger contacts) or to multiplesimultaneous contacts (e.g., “multitouch”/multiple finger contacts). Insome embodiments, contact/motion module 130 and display controller 156detect contact on a touchpad.

Contact/motion module 130 may detect a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns. Thus, a gesture may be detected by detecting a particularcontact pattern. For example, detecting a finger tap gesture includesdetecting a finger-down event followed by detecting a finger-up (liftoff) event at the same position (or substantially the same position) asthe finger-down event (e.g., at the position of an icon). As anotherexample, detecting a finger swipe gesture on the touch-sensitive surfaceincludes detecting a finger-down event followed by detecting one or morefinger-dragging events, and subsequently followed by detecting afinger-up (lift off) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the intensity of graphics that aredisplayed. As used herein, the term “graphics” includes any object thatcan be displayed to a user, including without limitation text, webpages, icons (such as user-interface objects including soft keys),digital images, videos, animations and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic may be assigned a corresponding code.Graphics module 132 receives, from applications etc., one or more codesspecifying graphics to be displayed along with, if necessary, coordinatedata and other graphic property data, and then generates screen imagedata to output to display controller 156.

Text input module 134, which may be a component of graphics module 132,provides soft keyboards for entering text in various applications (e.g.,contacts 137, e-mail 140, 1M 141, browser 147, and any other applicationthat needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing, to camera 143 as picture/video metadata,and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 may include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   contacts module 137 (sometimes called an address book or contact        list);    -   telephone module 138, which typically includes one or more        ringtones 139;    -   e-mail client module 140;    -   instant messaging (1M) module 141;    -   unlock screen module 142, which typically provides a screen        saver function;    -   camera module 143 for still and/or video images;    -   image management module 144;    -   browser module 147;    -   calendar module 148;    -   widget modules 149, which may include one or more of: weather        widget 149-1, pedometer widget 149-2, calculator widget 149-3,        alarm clock widget 149-4, dictionary widget 149-5, and other        widgets obtained by the user, as well as user-created widgets        149-6;    -   widget creator module 150 for making user-created widgets 149-6;    -   search module 151;    -   video and music player module 152, which may be made up of a        video player module and a music player module;    -   notes module 153;    -   map module 154; and/or    -   online video module 155.

Examples of other applications 136 that may be stored in memory 102include other word processing applications, other image editingapplications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, and text input module 134, contactsmodule 137 may be used to manage an address book or contact list (e.g.,stored in application internal state 192 of contacts module 137 inmemory 102 or memory 370), including: adding name(s) to the addressbook; deleting name(s) from the address book; associating telephonenumber(s), e-mail address(es), physical address(es) or other informationwith a name; associating an image with a name; categorizing and sortingnames; providing telephone numbers or e-mail addresses to initiateand/or facilitate communications by telephone 138, video conferencing,e-mail 140, or 1M 141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact module130, graphics module 132, and text input module 134, telephone module138 may be used to enter a sequence of characters corresponding to atelephone number, access one or more telephone numbers in an addressbook (e.g., using contacts module 137), modify a telephone number thathas been entered, dial a respective telephone number, conduct aconversation and disconnect or hang up when the conversation iscompleted. As noted above, the wireless communication may use any of aplurality of communications standards, protocols and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact module 130, graphics module132, text input module 134, contact list 137, and telephone module 138,a videoconferencing module (not shown) includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, e-mail client module 140 includes executable instructions tocreate, send, receive, and manage e-mail in response to userinstructions. In conjunction with image management module 144, e-mailclient module 140 makes it very easy to create and send e-mails withstill or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages may include graphics, photos, audio files, video filesand/or other attachments as are supported in a MMS and/or an EnhancedMessaging Service (EMS). As used herein, “instant messaging” refers toboth telephony-based messages (e.g., messages sent using SMS or MMS) andInternet-based messages (e.g., messages sent using XMPP, SIMPLE, orIMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, text inputmodule 134, GPS module 135, map module 154, and music player module 152,a workout support module includes executable instructions to createworkouts (e.g., with time, distance, and/or calorie burning goals);communicate with workout sensors (sports devices); receive workoutsensor data; calibrate sensors used to monitor a workout; select andplay music for a workout; and display, store and transmit workout data.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, text input module 134, and cameramodule 143, image management module 144 includes executable instructionsto arrange, modify (e.g., edit), or otherwise manipulate, label, delete,present (e.g., in a digital slide show or album), and store still and/orvideo images.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, and text inputmodule 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, e-mail client module 140, and browser module 147, calendarmodule 148 includes executable instructions to create, display, modify,and store calendars and data associated with calendars (e.g., calendarentries, to do lists, etc.) in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, and browser module 147, widget modules 149 aremini-applications that may be downloaded and used by a user (e.g.,weather widget 149-1, pedometer widget 149-2, calculator widget 149-3,alarm clock widget 149-4, and dictionary widget 149-5) or created by theuser (e.g., user-created widget 149-6). In some embodiments, a widgetincludes an HTML (Hypertext Markup Language) file, a CSS (CascadingStyle Sheets) file, and a JavaScript file. In some embodiments, a widgetincludes an XML (Extensible Markup Language) file and a JavaScript file(e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, and browser module 147, the widget creator module 150 may beused by a user to create widgets (e.g., turning a user-specified portionof a web page into a widget).

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, and text input module 134,search module 151 includes executable instructions to search for text,music, sound, image, video, and/or other files in memory 102 that matchone or more search criteria (e.g., one or more user-specified searchterms) in accordance with user instructions.

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, audio circuitry 110, speaker111, RF circuitry 108, and browser module 147, video and music playermodule 152 includes executable instructions that allow the user todownload and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present or otherwise play back videos (e.g., ontouch screen 112 or on an external, connected display via external port124). In some embodiments, device 100 may include the functionality ofan MP3 player, such as an iPod (trademark of Apple Inc.).

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, and text input module 134, notes module153 includes executable instructions to create and manage notes, to dolists, and the like in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, GPS module 135, and browser module 147, map module 154 maybe used to receive, display, modify, and store maps and data associatedwith maps (e.g., driving directions; data on stores and other points ofinterest at or near a particular location; and other location-baseddata) in accordance with user instructions.

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, audio circuitry 110, speaker111, RF circuitry 108, text input module 134, e-mail client module 140,and browser module 147, online video module 155 includes instructionsthat allow the user to access, browse, receive (e.g., by streamingand/or download), play back (e.g., on the touch screen or on anexternal, connected display via external port 124), send an e-mail witha link to a particular online video, and otherwise manage online videosin one or more file formats, such as H.264. In some embodiments, instantmessaging module 141, rather than e-mail client module 140, is used tosend a link to a particular online video.

Each of the above identified modules and applications correspond to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (i.e., sets of instructions) need notbe implemented as separate software programs, procedures or modules, andthus various subsets of these modules may be combined or otherwisere-arranged in various embodiments. In some embodiments, memory 102 maystore a subset of the modules and data structures identified above.Furthermore, memory 102 may store additional modules and data structuresnot described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 may be reduced.

The predefined set of functions that may be performed exclusivelythrough a touch screen and/or a touchpad include navigation between userinterfaces. In some embodiments, the touchpad, when touched by the user,navigates device 100 to a main, home, or root menu from any userinterface that may be displayed on device 100. In such embodiments, thetouchpad may be referred to as a “menu button.” In some otherembodiments, the menu button may be a physical push button or otherphysical input control device instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (in FIG. 1A) includes event sorter 170 (e.g., in operatingsystem 126) and a respective application 136-1 (e.g., any of theaforementioned applications 137-151 and 155).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripheral interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more views,when touch sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected may correspond to programmatic levels within aprogrammatic or view hierarchy of the application. For example, thelowest level view in which a touch is detected may be called the hitview, and the set of events that are recognized as proper inputs may bedetermined based, at least in part, on the hit view of the initial touchthat begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (i.e., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule, the hit view typically receives all sub-events related to thesame touch or input source for which it was identified as the hit view.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver module182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 may utilize or call data updater 176,object updater 177 or GUI updater 178 to update the application internalstate 192. Alternatively, one or more of the application views 191includes one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170, and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which may include sub-event delivery instructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch the eventinformation may also include speed and direction of the sub-event. Insome embodiments, events include rotation of the device from oneorientation to another (e.g., from a portrait orientation to a landscapeorientation, or vice versa), and the event information includescorresponding information about the current orientation (also calleddevice attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event 187 include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first lift-off (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second lift-off (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and lift-off of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event 187 alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers may interact with one another. In some embodiments, metadata183 includes configurable properties, flags, and/or lists that indicatewhether sub-events are delivered to varying levels in the view orprogrammatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module 145. In some embodiments, object updater 176 creates andupdates objects used in application 136-1. For example, object updater176 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput-devices, not all of which are initiated on touch screens, e.g.,coordinating mouse movement and mouse button presses with or withoutsingle or multiple keyboard presses or holds, user movements taps,drags, scrolls, etc., on touch-pads, pen stylus inputs, movement of thedevice, oral instructions, detected eye movements, biometric inputs,and/or any combination thereof, which may be utilized as inputscorresponding to sub-events which define an event to be recognized.

FIG. 2A-2E illustrate portable device 200 in accordance with someembodiments. Portable device 200 includes a subset of subsystems,components, and modules illustrated in FIGS. 1A-1B. For example,portable device 200 optionally includes all the subsystems, components,and modules illustrated in FIGS. 1A-1B (i.e., portable device 200 mayinclude portable multifunction device 100). Alternatively, portabledevice 200 is a telephone device having less than all the modules orcomponents illustrated in FIGS. 1A-1B. In some embodiments, portabledevice 200 includes touch screen 112.

FIG. 2A is a high-level exploded view of portable device 200 inaccordance with some embodiments. In FIG. 2A, portable device 200includes an enclosure (e.g., front cover 202 and back cover 204). Touchscreen 112 is coupled with front cover 202. Between front cover 202 andback cover 204 is circuit board 208. Circuit board 208 typicallyincludes at least a subset of components illustrated in FIG. 1A (e.g.,processor(s) 120 and controller 122), some of which are omitted in FIG.2A for brevity. Circuit board 208 includes actuator 210 for generatingmechanical vibrations and sensor 220 for detecting mechanicalvibrations. In some embodiments, actuator 210 includes actuator 127(FIG. 1A, such as a motor) and/or speaker 111 (FIG. 1A). In someembodiments, sensor 220 includes accelerometer 168 (FIG. 1A), and/orvibration sensor 129 (FIG. 1A).

Although depicted as two separate elements, actuator 210 and sensor 220may be packaged together as a single component (or a same device).Therefore, in some embodiments, portable device 200 includes atransducer that is configured to generate mechanical vibrations and alsodetect mechanical vibrations (e.g., by generating electrical signals inresponse to mechanical vibrations). In some embodiments, the transducerincludes a piezo transducer (e.g., a piezoelectric transducer) or audiospeaker 111 (FIG. 1A).

Although depicted as two separate elements (e.g., front cover 202 andback cover 204), the enclosure may be integrally formed as a singleelement. Alternatively, the enclosure may comprise three or moreelements.

Although FIG. 2A depicts an embodiment of portable device 200 with asingle actuator and a single sensor, portable device 200 may include aplurality of actuators and sensors. FIG. 2B is another high-levelexploded view of portable device 200 in accordance with someembodiments. In FIG. 2B, a plurality of actuators (e.g., actuators 210-1through 210-4) and a plurality of sensors (e.g., sensors 220-1 through220-4) are located on the inner surface of back cover 204 (e.g., thesurface facing circuit board 208). Alternatively, actuators 210 andsensors 220 are located on the outer surface of back cover 204 (e.g.,the surface facing away from circuit board 208) or embedded in backcover 204.

FIG. 2C is yet another high-level exploded view of portable device 200in accordance with some embodiments. In FIG. 2C, actuators and sensorsare included in subsystem 230 which is placed underneath, or embeddedin, touch screen 112. For example, subsystem 230 includes a layer ofpiezoelectric material deposited underneath touch screen 112 forgenerating mechanical vibrations and detecting mechanical vibrations. Insome embodiments, the layer of piezoelectric material in subsystem 230is patterned to form a plurality of piezoelectric components. In someembodiments, the plurality of piezoelectric components includes one ormore piezoelectric components for generating mechanical vibrations andone or more separate piezoelectric components for detecting mechanicalvibrations.

FIGS. 2D and 2E illustrate portable devices 200 having subsystems 232,in accordance with some embodiments. In some embodiments, each subsystem232 corresponds to subsystem 230 depicted in FIG. 2C. In other words,each subsystem 232 includes one or more actuators and one or moresensors. In FIG. 2D, portable device 200 includes one or more of:subsystem 232-1 on or in the back enclosure, subsystem 232-2 on or inthe side of the enclosure, and subsystem 232-3 on or in the frontenclosure. Portable device 200 may include a subsystem on or in the topand/or bottom side of the enclosure.

In FIG. 2E, portable device 200 includes a plurality of subsystems 232.In some embodiments, the plurality of subsystems 232 is not uniformlydistributed. In some embodiments, the plurality of subsystems 232 ismore densely positioned along the edges than near the center, or viceversa (not shown). In some embodiments, a plurality of subsystems 232 ispositioned along the edges of portable device 200, and are not locatednear the center of a respective surface, such as the front surface, ofdevice 200 (not shown).

As shown in FIGS. 2A-2E, portable device 200 includes one or moreactuators and one or more sensors. The number of actuators in portabledevice 200 need not match the number of sensors in portable device 200(i.e., the number of actuators is different from the number of sensors).Furthermore, the actuators need not be located on the same surface asthe sensors (e.g., at least one actuator is located on circuit board208, and at least one sensor is located on back cover 204). In fact,actuators and sensors may be located anywhere in or on the enclosure ofthe device (e.g., actuators and sensors may be located on or in each offront cover 202, circuit board 208, and back cover 204).

FIG. 3 illustrates exemplary actuator input provided to an actuator(e.g., actuator 210, FIG. 2A) and an exemplary sensor signal detected bya sensor (e.g., sensor 220, FIG. 2A) in accordance with someembodiments. The actuator input and the sensor signal are plotted asfunctions of time (e.g., each horizontal axis represents time, and eachvertical axis represents an intensity or amplitude of a respective inputor signal). It should be appreciated that the actuator input and thesensor signal illustrated in FIG. 3 are prophetic examples, and are notdrawn to scale.

In FIG. 3, the illustrated actuator input and the sensor signal havesinusoidal waveforms. The actuator input has amplitude A1, and thesensor signal has amplitude A2. As illustrated, the actuator input andthe sensor signal has a phase difference, d. The amplitude A2 and thephase difference d of the sensor correspond to changes in response toone or more touches on the enclosure of portable device 200 (e.g., fromS1 to S2). For example, when a user grabs portable device 200 with afirm grip, the amplitude of the sensor signal is lower compared to whenthe user grabs portable device 200 with a light grip. Typically, thephase difference d also changes in response to the grip strength.Therefore, the amplitude A2 and/or the phase difference d can be used todetermine the grip strength.

In addition, in some embodiment the amplitude A2 and phase difference dare obtained from multiple sensors, thereby providing multiple signalsfrom which determine grip strength, position, etc. Further, theamplitude A2 and the phase difference d at any one sensor may varydepending on a number of contacts on the enclosure (e.g., one finger v.two fingers), the overall area contacted by the contacts (e.g., onefinger v. entire palm), and a distance from a respective sensor to alocation of a respective contact. Therefore, the amplitude A2 and/or thephase difference d from one or more sensors can be used to determine oneor more locations of one or more contacts and/or a holding state (e.g.,held by a thumb and an index finger v. held by five fingers and a palm).Similarly, the amplitude A2 and/or the phase difference d from one ormore sensors can be used to determine whether the device is held with aleft-hand or a right-hand (e.g., one or more sensors located near a palmof a holding hand will detect a larger contact area than one or moresensors located near fingers). Furthermore, the amplitude A2 and thephase difference d may also vary depending on mechanical properties ofthe contacts (e.g., contacts made with a finger v. contacts made byclothing). Therefore, the amplitude A2 and/or the phase difference dfrom one or more sensors can be used to determine an environment ofportable device (e.g., in a pocket or a bag v. hand-held).

Although the actuator input and the sensor signal are depicted as havingsinusoidal waveforms, other waveforms may be used. For example, theactuator input may include a square wave, a triangle wave, a sawtoothwave, or a superposition of multiple waveforms. In some embodiments,other properties of the sensor signal (e.g., rise time and/or fall time)may be used in addition to, or instead of, at least one of the amplitudeA2 and the phase difference d in determining the holding state of thedevice. Furthermore, the actuator input and the sensor signal need notbe continuous. Especially when a single transducer is used for bothgenerating and detecting mechanical vibrations, a discrete signal (e.g.,a step function or a top-hat function) may be provided as an input tothe transducer, and a subsequent response (e.g., rise time or fall time)may be monitored. When portable device 200 includes a plurality ofactuators (e.g., 210-1 through 210-4 in FIG. 2B, and/or subsystems 232in FIG. 2E), the plurality of actuators need not generate mechanicalvibrations simultaneously or harmonically. In some embodiments, theplurality of actuators is configured to generate mechanical vibrationsin accordance with a predefined pattern. The predefined pattern definesat least the timing and duration for generation of mechanical vibrationsby respective actuators.

At least in some embodiments, each actuator generates mechanicalvibrations of a respective frequency and amplitude such that themechanical vibrations are not perceived by a user of portable device200. For example, the frequency may be set below or above a hearingrange (e.g., 20 Hz to 20 kHz). Alternatively, the frequency is withinthe hearing range, but the amplitude is set sufficiently low that theuser cannot hear the mechanical vibrations or is unlikely to hear themechanical vibrations. Similarly, the amplitude and frequency may be setso that the user may not feel the mechanical vibrations by touch.

Associated Processes

Attention is now directed towards embodiments of associated processesthat may be implemented on a portable device with one or more actuatorsand one or more sensors, such as portable multifunction device 100 orportable device 200.

FIGS. 4A-4C are flow diagrams illustrating method 400 of conditionallymodifying an operation of a device in accordance with some embodiments.Method 400 is performed at a portable electronic device (e.g., portablemultifunction device 100, FIG. 1) having an enclosure, one or moreactuators and one or more sensors. In some embodiments, the one or moreactuators are located in or on the enclosure, and the one or moresensors are located in or on the enclosure. The portable device includesone or more processors for executing one or more programs, and memorystoring one or more programs for execution by the one or moreprocessors. In some embodiments, the portable electronic device includesa display and/or a touch-sensitive surface. In some embodiments, thedisplay is a touch screen display and the touch-sensitive surface is onthe display. In some embodiments, the display is separate from thetouch-sensitive surface. In various implementations, some operations ofmethod 400 may be combined and/or the order of some operations may bechanged.

The device generates (402) mechanical vibrations with the one or moreactuators (e.g., actuators 127 and/or speaker 111 in FIG. 1A, actuators210 in FIGS. 2A-2B, or subsystems 230 and/or 232 in FIGS. 2C-2E).

The device detects (404) mechanical vibrations with the one or moresensors (e.g., sensors 129 and/or accelerometers 168 in FIG. 1A, sensors220 in FIGS. 2A-2B, or subsystems 230 and/or 232 in FIGS. 2C-2E).

The device analyzes (406) one or more signals produced by the one ormore sensors with respect to mechanical vibrations to determine aholding state of the portable device (e.g., based on the amplitude,phase, or any other properties of mechanical vibrations). For example,the device may determine that the device is held by a hand, left on ahard surface (e.g., a tabletop), or surrounded by clothing (e.g., in apocket or in a bag); and if held by a hand, the number of fingersholding the device and/or whether a palm is contacting the device.

The device modifies (408) operation of at least one application (e.g.,any of modules or widgets depicted in FIG. 1A) executed by the one ormore processors in accordance with the determined holding state. In someimplementations, operation 408 comprises conditionally modifyingoperation of at least one application in accordance with the determinedholding state. In some circumstances, the device does not modify theoperation in accordance with the determined holding state, and as aresult a default operation is performed.

In some embodiments, the analyzing includes (410) determining a gripstrength of a user's hold on the portable device. In some embodiments,the grip strength is a value determined on a continuous orsemi-continuous scale (e.g., 0 to 1). In some embodiments, determiningthe grip strength includes classifying the grip strength into one ofpredefined categories (e.g., not held, regular grip, and tight grip).

In some embodiments, the modifying includes (412) modifying a userinterface response to a user gesture in accordance with the determinedgrip strength. In some embodiments, the device modifies a response to aswipe gesture in response to a tight grip so that a displayed userinterface element scrolls less in response to the swipe gesture. In someembodiments, the device modifies a displayed user interface in responseto a tight grip such that a portion of the displayed user interface iszoomed in so as to assist a user to provide an accurate touch input. Insome embodiments, the device modifies an auto-correction orauto-suggestion function so that the auto-correction or auto-suggestionfunction provides a result distinct from a result that would be providedwith a regular grip. In some embodiments, in response to a determinationthat no grip is detected on the device, the device increases a volumeand length of a ringtone that is played in response to an incoming callor message (e.g., so that a user can better hear the ringtone). In someembodiments, in response to the determination that no grip is detectedon the device, the device increases a volume but decreases a length of aringtone (e.g., so as not to interrupt the user for long and also toreduce battery usage (i.e., reduce the amount of power drawn from thebattery)). In some embodiments, in response to the determination that nogrip is detected on the device, the device changes a ringtone to adifferent sound or music, or increases the amplitude of signalingvibrations that are generated in response to an incoming call ormessage.

In some embodiments, the modifying includes (414) modifying a scrollspeed in response to a user scrolling gesture in accordance with thedetermined grip strength. For example, in accordance with adetermination that the device is held with a regular grip, the deviceresponds to a swipe gesture by scrolling a graphical user interface at afirst speed. In accordance with a determination that the device is heldwith a tight grip, the device responds to a swipe gesture by scrolling agraphical user interface at a second speed lower than the first speed.This allows a user to more accurately scroll when the device is heldwith a tight grip.

In some embodiments, the portable device further includes (416) atouch-sensitive surface. The device analyzes the one or more signalsproduced by the one or more sensors with respect to mechanicalvibrations to determine a touch strength on the touch-sensitive surface(e.g., how hard a contact is pressed onto the touch-sensitive surface),and modifies operation of at least one application executed by the oneor more processors in accordance with the determined touch strength. Insome embodiments, in accordance with a determination that a finger ispressed with a normal pressure on the touch-sensitive surface, thedevice scrolls a graphical user interface at a first speed, and inaccordance with a determination that the finger is pressed hard on thetouch-sensitive surface, the device scrolls a graphical user interfaceat a second speed lower than the first speed so that the user can moreaccurately scroll the graphical user interface.

The device typically includes a ringtone that is played at the portabledevice in response to an incoming call. In some embodiments, the devicemodifies (418) a length of the ringtone at least in accordance with thedetermined holding state. For example, the device may shorten the lengthwhen the portable device is determined to be located on a hard surface,for example a table, or already in a hand. The device may increase thelength when the portable device is determined to be located in a pocketso that the user has more time to take the portable device out of thepocket.

In some embodiments, an application in the one or more programs isconfigured to light up the display by default in response to an input onone or more manual user input devices (e.g., a touch-sensitive displayor a key or button) of the portable device. For example, an unlockscreen application (e.g., unlock screen module 142, FIG. 1A), like ascreen saver, keeps the display off or shows a blank screen on thedisplay when the device has not been used for a predefined time, and inresponse to an input on one or more manual user input devices, theunlock screen application displays an unlock screen. The deviceconditionally modifies (420) the application in accordance with at leastthe determined holding state such that the application conditionallydoes not light up a display of the portable device. For example, inaccordance with a determination that the device is stored in a pocket ora bag (e.g., which may be determined, for example, by detecting that thedevice is not being handheld and is not resting on a hard surface), thedevice prevents the unlock screen application from lighting up thedevice's display, even if the touch-sensitive display is detecting atouch or contact with the display, so as to preserve the device'sbattery power.

In some embodiments, the device detects (422, FIG. 4B) ambientbrightness with a light sensor of the portable device (e.g., usingoptical sensor(s) 164, FIG. 1A), and modifies operation of at least oneapplication executed by the one or more processors in accordance withthe determined holding state and the ambient brightness. The combinationof the holding state and the ambient brightness improves accuracy, forexample, in determining whether the device is stored in a pocket or in abag (where the ambient brightness is low).

The device typically includes a ringtone that is played at the portabledevice in response to an incoming call. In some embodiments, the devicemodifies (424) a length of the ringtone at least in accordance with thedetermined holding state and the ambient brightness. For example, thedevice may increase the length when the device is determined to be notheld (e.g., based on the absence of finger contacts) and located in apocket (e.g., based at least on the ambient brightness).

In some embodiments, an application in the one or more programs isconfigured to light up a display of the portable device by default inresponse to an input on one or more manual user input devices of theportable device (e.g., unlock screen module 142, FIG. 1A). The deviceconditionally modifies (426) the application in accordance with thedetermined holding state and the ambient brightness such that theapplication conditionally does not light up the display. For example,when the device is determined to be in a pocket or a bag, based on botha lack of ambient light and the device's holding state, the deviceprevents the device's unlock screen application from lighting up thedevice's display, even if the touch-sensitive display is detecting atouch or contact with the display, so as to preserve the device'sbattery power.

In some embodiments, the device launches (428) a pedometer application(e.g., pedometer widget 149-2, FIG. 1A) in accordance with thedetermined holding state and the ambient brightness. For example, thedevice launches the pedometer application when the portable device isdetermined to be located in a pocket (e.g., based on the absence offinger contacts and/or based on the touches by clothing) and whenrhythmical motions of the device (motions corresponding to walking) aredetected (e.g., by using accelerometer(s) 168, FIG. 1A).

In some embodiments, the device detects (430) an acceleration of theportable device using at least one accelerometer of the portable device,and modifies operation of at least one application executed by the oneor more processors in accordance with the determined holding state andthe acceleration of the portable device. For example, the device maydetermine that the device is being carried by a user who is in avehicle, and modify or change the ringtone accordingly (e.g., reduce thevolume).

The device typically includes a ringtone that is played at the portabledevice in response to an incoming call. In some embodiments, the devicemodifies (432) a length of the ringtone at least in accordance with thedetermined holding state and the acceleration of the portable device.For example, the device increases the length of the ringtone when theportable device is in a pocket of a running user so that the user canbetter hear the ringtone.

In some embodiments, the device determines (434, FIG. 4C) one or morelocations of one or more contacts by a user on the enclosure of theportable device in accordance with the one or more signals produced bythe one or more sensors.

In some embodiments, the device identifies (436) a user in accordancewith the one or more locations of the one or more contacts. For example,a respective user has a respective hand size and a respective style ofholding the device. Such information may be used to improve the securityof the device. In some embodiments, the respective user may at leasttemporarily grab the device at combination of locations consistent withthe user's hand size and style of holding the device, enabling thedevice to identify the device holder as the respective user. In someembodiments, the device determines grip strength of a user's hold on theportable device, and identifies the user in accordance with the one ormore locations of the one or more contacts and respective grip strengths(e.g., more support on the index finger v. middle finger).

For touch-sensitive displays, the detected contact area of a finger istypically converted to a coordinate tuple (an (x, y) position or point).The coordinate tuple is then used (like the point of a cursor in adevice with mouse-based input) to interact with and manipulate the userinterface objects on the touch-sensitive display. The conversion of thetwo-dimensional finger contact area to a one-dimensional point (e.g.,coordinate tuple) often requires careful adjustment. The centroid of thefinger contact area typically does not correspond to the location thatis perceived by a user as being touched. This may cause touch targetingerrors when the user is trying to activate keys on a virtual keyboard orinteract with other objects on the touch-sensitive display. The changein viewing parallax in different areas of the touch screen and thedifferences in contact areas between thumbs and other fingers may alsolead to touch targeting errors and incorrect manipulations. Undoingerroneous manipulations and repeating touch inputs creates a significantcognitive burden on a user and may lead to user frustration. Inaddition, correcting touch inputs takes additional time, thereby wastingboth human and device resources (e.g., time and battery power). Thislatter consideration is particularly important in battery-operateddevices.

Therefore, in some embodiments, the device receives (438) one or moreuser contact areas on a touch-sensitive surface of the portable device;determines, for each user contact area, a respective finger contactcoordinate tuple based on a respective location of a respective fingercontact area and the determined holding state; and manipulates at leastone of one or more user interface objects displayed on a display of theportable device in accordance with the one or more respective fingercontact coordinate tuples. Thus, operation of device is modified bymodifying the finger contact coordinate tuple based on the determinedholding state.

FIG. 5 is a flow diagram illustrating method 500 of conditionallyanswering an incoming call in accordance with some embodiments. Method500 is performed at a portable telephone device (e.g., portable device200, FIG. 2A) with an enclosure, one or more processors for executingone or more programs, one or more actuators in or on the enclosure, oneor more sensors in or on the enclosure, and memory storing one or moreprograms for execution by the one or more processors. The portabletelephone device may include portable multifunction device 100illustrated in FIG. 1. However, the portable telephone device requiresmodules and components necessary for its function as a portabletelephone, and need not include all the modules and componentsillustrated in FIG. 1 (e.g., the portable telephone device may notinclude one or more of: touch-sensitive display system 112, proximitysensor 166, weather widget(s) 149-1, and widget creator module 150).

The device generates (502) mechanical vibrations with the one or moreactuators (e.g., actuators 127 and/or speaker 111 in FIG. 1A, actuators210 in FIGS. 2A-2B, or subsystems 230 and/or 232 in FIGS. 2C-2E).

The device detects (504) mechanical vibrations with the one or moresensors (e.g., sensors 129 and/or accelerometers 168 in FIG. 1A, sensors220 in FIGS. 2A-2B, and subsystems 230 and 232 in FIGS. 2C-2E).

The device analyzes (506) one or more signals produced by the one ormore sensors with respect to mechanical vibrations to determine aholding state of the portable telephone device (e.g., based on theamplitude, phase, or any other properties of mechanical vibrations).

The device conditionally answers (508) an incoming call in accordancewith a change in the determined holding state of the portable telephonedevice (e.g., answer an incoming call when the portable device is pickedup from a hard surface, for example a table top).

As described herein, method 500 provides an intuitive way to answer anincoming call. The method reduces the cognitive burden on a user whenanswering an incoming call, thereby creating a more efficienthuman-machine interface.

The operations in the information processing methods described above maybe implemented by running one or more functional modules in informationprocessing apparatus such as general purpose processors or applicationspecific chips. These modules, combinations of these modules, and/ortheir combination with general hardware (e.g., as described above withrespect to FIGS. 1A and 3) are all included within the scope ofprotection of the invention.

The operations described above with reference to FIGS. 4A-4B and FIG. 5may be implemented by components depicted in FIGS. 1A-1B. For example,detection operation 404, modifying operation 408, and conditionalanswering operation 508 may be implemented by event sorter 170, eventrecognizer 180, and event handler 190. Event monitor 171 in event sorter170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first event (e.g., grabbing a phone) corresponds toa predefined event or sub-event, such as answering an incoming call.When a respective predefined event or sub-event is detected, eventrecognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 may utilize orcall data updater 176 or object updater 177 to update the applicationinternal state 192. In some embodiments, event handler 190 accesses arespective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 6 shows a functional blockdiagram of a portable electronic device 600 configured in accordancewith the principles of the invention as described above. The functionalblocks of the device may be implemented by hardware, software, or acombination of hardware and software to carry out the principles of theinvention. It is understood by persons of skill in the art that thefunctional blocks described in FIG. 6 may be combined or separated intosub-blocks to implement the principles of the invention as describedabove. Therefore, the description herein may support any possiblecombination or separation or further definition of the functional blocksdescribed herein.

As shown in FIG. 6, a portable electronic device 600 includes anactuator unit 604 for generating mechanical vibrations; a sensor unit606 for detecting mechanical vibrations; and a processing unit 618coupled to the actuator unit 604 and the sensor unit 606. In someembodiments, the portable electronic device 600 includes an enclosure602 that encloses processing unit 618, and optionally encloses otherones of the units of portable electronic device 600 described herein. Insome embodiments, some of the units of portable electronic device 600are mounted on enclosure 602, while others are enclosed within enclosure602. In some embodiments, the processing unit 618 includes an analyzingunit 620, a modifying unit 622, a determining unit 624, a detecting unit626, a launching unit 628, an identifying unit 630, a receiving unit632, a manipulating unit 634, and a lighting up unit 636.

The processing unit 618 is configured to analyze one or more signalsproduced by the sensor unit 606 with respect to mechanical vibrations todetermine a holding state of the portable device 600; and modifyoperation of at least one application executed by the processing unit618 in accordance with the determined holding state.

In some embodiments, the sensor unit 606 and the actuator unit 604comprise a same device.

In some embodiments, the sensor unit 606 includes a piezo transducer.

In some embodiments, the processing unit 618 is configured to determinea grip strength of a user's hold on the portable device 600 (e.g., withthe determining unit 624).

In some embodiments, the processing unit 618 is configured to modify auser interface response to a user gesture in accordance with thedetermined grip strength (e.g., with the modifying unit 622).

In some embodiments, the processing unit 618 is configured to modify ascroll speed in response to a user scrolling gesture in accordance withthe determined grip strength (e.g., with the modifying unit 622).

In some embodiments, the portable device 600 includes a touch-sensitivesurface unit 608. The processing unit 618 is configured to analyze theone or more signals produced by the sensor unit 606 with respect tomechanical vibrations to determine a touch strength on thetouch-sensitive surface unit 608. The processing unit 618 is configuredto modify operation of at least one application executed by theprocessing unit 618 in accordance with the determined touch strength.

In some embodiments, the processing unit 618 is configured to modify alength of a ringtone at least in accordance with the determined holdingstate (e.g., with the modifying unit 622).

In some embodiments, the portable device 600 includes a display unit 610and a manual input device unit 612. The processing unit 618 isconfigured to light up the display unit 610 by default in response to aninput on the manual input device unit 612 (e.g., with the lighting upunit 636). The processing unit 618 is configured to modify operation ofthe processing unit 618 (e.g., with the modifying unit 622) inaccordance with at least the determined holding state such that theprocessing unit 618 conditionally does not light up the display unit610.

In some embodiments, the portable device 600 includes a light sensorunit 614. The processing unit 618 is configured to detect ambientbrightness with the light sensor unit 614 (e.g., with the detecting unit626); and the processing unit 618 is configured to modify operation ofthe processing unit 618 in accordance with the determined holding stateand the ambient brightness (e.g., with the modifying unit 622).

In some embodiments, the processing unit 618 is configured to modify thelength of a ringtone in accordance with the determined holding state andthe ambient brightness (e.g., with the modifying unit 622).

In some embodiments, the portable device 600 includes a display unit 610and a manual user input device unit 612. The processing unit 618 isconfigured to light up the display unit 610 by default in response to aninput on the manual input device unit 612 (e.g., with the lighting upunit 630); and the processing unit 618 is configured to conditionallymodify operation of the processing unit 618 (e.g., with the modifyingunit 622) in accordance with the determined holding state and theambient brightness such that the processing unit 618 conditionally doesnot light up the display unit 610.

In some embodiments, the processing unit 618 is configured to launch apedometer application in accordance with the determined holding stateand the ambient brightness (e.g., with the launching unit 628).

In some embodiments, the portable device 600 includes a accelerometerunit 616. The processing unit 618 is configured to detect anacceleration of the portable device 600 using the accelerometer unit 616(e.g., with the detecting unit 626); and the processing unit 618 isconfigured to modify operation of the processing unit 618 in accordancewith the determined holding state and the acceleration of the portabledevice 600 (e.g., with the modifying unit 622).

In some embodiments, the processing unit 618 is configured to modify thelength of a ringtone in accordance with the determined holding state andthe acceleration of the portable device 600 (e.g., with the modifyingunit 622).

In some embodiments, the processing unit 618 is configured to determineone or more locations of one or more contacts by a user on the enclosure602 of the portable device 600 in accordance with the one or moresignals produced by the sensor unit 606.

In some embodiments, the processing unit 618 is configured to identify auser in accordance with the one or more locations of the one or morecontacts (e.g., with the identifying unit 630).

In some embodiments, the portable device 600 includes a display unit 610and a touch-sensitive surface unit 608. The processing unit 618 isconfigured to: receive one or more user contact areas on thetouch-sensitive surface unit 608 (e.g., with the receiving unit 632);determine, for each user contact area, a respective finger contactcoordinate tuple based on a respective location of a respective fingercontact area and the determined holding state (e.g., with thedetermining unit 624); and manipulate at least one of one or more userinterface objects displayed on the display unit 610 in accordance withthe one or more respective finger contact coordinate tuples (e.g., withthe manipulating unit 634).

In accordance with some embodiments, FIG. 7 shows a functional blockdiagram of a portable telephone device 700 configured in accordance withthe principles of the invention as described above. The functionalblocks of the device may be implemented by hardware, software, or acombination of hardware and software to carry out the principles of theinvention. It is understood by persons of skill in the art that thefunctional blocks described in FIG. 7 may be combined or separated intosub-blocks to implement the principles of the invention as describedabove. Therefore, the description herein may support any possiblecombination or separation or further definition of the functional blocksdescribed herein.

As shown in FIG. 7, a portable telephone device 700 includes an actuatorunit 704 for generating mechanical vibrations; a sensor unit 706 fordetecting mechanical vibrations; and a processing unit 710 coupled tothe actuator unit 704 and the sensor unit 706. In some embodiments, theprocessing unit 710 includes an analyzing unit 712, and an answeringunit 716.

The processing unit 710 is configured to: analyze one or more signalsproduced by the sensor unit 706 with respect to mechanical vibrations todetermine a holding state of the portable telephone device 700 (e.g.,using the analyzing unit); and conditionally answer an incoming call inaccordance with a change in the determined holding state of the portabletelephone device 700 (e.g., using the answering unit).

In some embodiments, portable telephone device 700 includes an enclosure702 that encloses processing unit 710, and optionally encloses otherones of the units of portable telephone device 700 described herein. Insome embodiments, some of the units of portable telephone device 700 aremounted on enclosure 702, while others are enclosed within enclosure702.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the invention and its practical applications, to therebyenable others skilled in the art to best utilize the invention andvarious embodiments with various modifications as are suited to theparticular use contemplated

We claim:
 1. A computing device, comprising: a processor; and a memoryfor storing instructions which, when executed by the processor performsa method for operating the computing device, the method comprising:receiving a first touch input on a touch-sensitive surface of thecomputing device, the first touch input having a first amount ofpressure; in response to receiving the first touch input, causing anapplication executing on the computing device to provide a first outputon a display; receiving a second touch input on the touch-sensitivesurface of the computing device, the second touch input having a secondamount of pressure that is different than the first amount of pressure;and in response to receiving the second touch input, causing theapplication executing on the computing device to provide a second outputon the display that is different than the first output.
 2. The computingdevice of claim 1, further comprising at least one sensor, wherein theat least one sensor is configured to determine the first amount ofpressure and the second amount of pressure.
 3. The computing device ofclaim 1, wherein the first touch input is a gesture.
 4. The computingdevice of claim 1, wherein the second touch input is a gesture.
 5. Thecomputing device of claim 1, wherein at least one of the first touchinput and the second touch input is provided by a stylus.
 6. A methodfor operating a computing device, comprising: receiving a touch input ona touch-sensitive surface; determining an amount of pressure of thetouch input; causing an application being executed on the computingdevice to provide a first output on a display of the computing device inresponse to a determination that a first amount of pressure is receivedby the touch-sensitive surface; and causing the application beingexecuted on the computing device to provide a second output on thedisplay of the computing device in response to a determination that asecond amount of pressure is received by the touch-sensitive surface. 7.The method of claim 6, wherein the touch input is provided by a stylus.8. The method of claim 6, wherein the touch input is a gesture.
 9. Themethod of claim 6, further comprising determining a holding state of thecomputing device based on feedback received from one or more sensorsassociated with the computing device.
 10. A non-transitorycomputer-readable medium storing computer-executable instructions which,when executed by a processor perform a method for operating a computingdevice, comprising: receiving a first touch input on a touch-sensitivesurface of the computing device, the first touch input having a firstamount of pressure; in response to receiving the first touch input,causing an application executing on the computing device to provide afirst output on a display; receiving a second touch input on thetouch-sensitive surface of the computing device, the second touch inputhaving a second amount of pressure that is different than the firstamount of pressure; and in response to receiving the second touch input,causing the application executing on the computing device to provide asecond output on the display that is different than the of output. 11.The non-transitory computer-readable medium of claim 10, furthercomprising at least one sensor, wherein the at least one sensor isconfigured to determine the first amount of pressure and the secondamount of pressure.
 12. The non-transitory computer-readable medium ofclaim 10, wherein the first touch input is a gesture.
 13. Thenon-transitory computer-readable medium of claim 10, wherein the secondtouch input is a gesture.
 14. The non-transitory computer-readablemedium of claim 10, wherein at least one of the first touch input andthe second touch input is provided by a stylus.
 15. The computing deviceof claim 1, further comprising an actuator operative to provide avibration in response to the first touch input.
 16. The computing deviceof claim 1, further comprising an actuator operative to provide avibration in response to the second touch input.
 17. The method of claim6, further comprising providing a vibration when the first amount ofpressure is received by the touch-sensitive surface.
 18. The method ofclaim 6, further comprising providing a vibration when the second amountof pressure is received by the touch-sensitive surface.
 19. Thenon-transitory computer-readable medium of claim 10, further comprisinginstructions for causing an actuator to provide a vibration in responseto the first touch input.
 20. The non-transitory computer-readablemedium of claim 10, further comprising instructions for causing anactuator to provide a vibration in response to the second touch input.